Fix panic in SET AUTHORIZATION parsing when scope modifier is missing
#2201
+20
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iffyio
reviewed
Feb 7, 2026
iffyio
approved these changes
Feb 10, 2026
Contributor
iffyio
left a comment
iffyio
left a comment
There was a problem hiding this comment.
LGTM! Thanks @LucaCappelletti94!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Parsing
SET AUTHORIZATION <value>without a scope modifier (e.g.SESSION,LOCAL) causes a panic due to an.expect()call on aNonevalue inparse_set. This was discovered via a fuzz-like input string but is trivially reproducible with anySET AUTHORIZATION ...statement that omits the scope keyword.The panic occurs at mod.rs:
Valid SQL requires a scope modifier, e.g.
SET SESSION AUTHORIZATION 'user', so the missing scope is indeed an error — but it should be a gracefulParserError, not a panic.Closes #2200